docs: clarify register validation rules vs native HTML attributes#1209
Merged
bluebill1049 merged 1 commit intoreact-hook-form:masterfrom May 2, 2026
Conversation
Contributor
|
@dfedoryshchev is attempting to deploy a commit to the BEEKAI OSS Team on Vercel. A member of the Team first needs to authorize it. |
✅ Deploy Preview for sage-cassata-31d224 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
bluebill1049
approved these changes
May 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1043.
The register Options table doesn't say whether the listed entries (
required,maxLength, etc.) are validation rules or native HTML attributes. They're validation rules tied tomode; the native HTML attributes only get forwarded whenprogressive: trueis set onuseForm(seesrc/logic/createFormControl.ts:1111-1119in the library repo, which is also already linked fromuseform.mdx:101and documented atuseform/form.mdx:62-78).Adds a 4-line
noteadmonition above theTabGroupso it applies to both tabs. No row text changes, no prettier reflow.